NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/lang/c++-part2/15283

Internet Message Format | 1996-08-05 | 1.7 KB

Path: wdl1.wdl.loral.com!dst17!mab
From: [e-mail] (Mark A Biggar)
Newsgroups: alt.computer.consultants,comp.edu,comp.lang.basic.misc,comp.lang.c++,comp.lang.misc,comp.lang.pascal.borland,comp.lang.pascal.delphi.misc,comp.misc,comp.os.msdos.programmer,comp.os.os2.programmer.misc,comp.programming
Subject: Re: Info on being a Systems Programmer/Analyst?
Date: 4 Apr 1996 16:13:47 GMT
Organization: Loral Western Development Labs
Message-ID: <4k0sfr$[e-mail]>
References: <[e-mail]> <4j0pha$[e-mail]> <4j72t8$[e-mail]>
NNTP-Posting-Host: dst17.wdl.loral.com

In article <4j72t8$[e-mail]> [e-mail] (This space intentionally left blank) writes:
>And if you ever get stuck and can't see the problem no matter how many
>dozens of hours you've looked for it, explain your frustrations to another
>programmer, have them glance at your code, and 9 times out of 10 they will
>see the problem within 30 seconds...  :^)
>Don't feel too bad about this...you'll spot their "killer problem" in under
>30 seconds some day too...nobody knows why, but this does happen.  A lot.

Actually, you will find that more often YOU will discover your own problem
in the course of trying to describe it to your fellow programmer.  The other
person doesn't even have to be a programmer for this to work.  Note that
there is a formal process based on this, called Walkthroughs or Inspections
that a lot of companies use.  A formal Inspection process it probably the
easest thing you can do to improve the quality of the software you produce,
and will always reduces the number of errors that eventually still exist in
you final product.

--
Mark Biggar
[e-mail]